Verdict

Approve. Trivial, correct alignment of user-facing CLI hints with the documented bun-based workflow (CLAUDE.md:23 and AGENTS.md:65 both call out bun as the workspace package manager and explicitly say "NOT pnpm"). Each replacement is verified against the corresponding package.json script.

Verified:

• packages/studio/package.json defines "dev": "vite" → spawn("bun", ["run", "dev"]) is equivalent to the previous pnpm exec vite.
• packages/player/package.json defines "build": "tsup" → bun run --cwd packages/player build builds the player as expected.
• Root package.json defines "build" (orchestrates all packages) → bun run build is the correct root-level build.
• Author's stated scope is right: pnpm references in installerDetection.ts / autoUpdate.ts are correctly left alone — those detect end-user global installs and pnpm-installed users still need the pnpm add -g upgrade hint.

Key Concerns

(none)

Test Coverage

No test changes needed — these are message-string and command-name updates. The studioServer HTML snippet and the play/preview error paths are infrequent fallback branches; existing tests don't (and don't need to) snapshot the literal text.

Nits / Future

• packages/cli/src/commands/play.ts:28,36 and packages/cli/src/server/studioServer.ts:412 — bun run build is ambiguous about the working directory (it's a root-level script). The original pnpm build had the same ambiguity, so this isn't a regression, but contributor-facing hints could be made explicit, e.g. bun run build from the monorepo root or bun run --cwd <repo-root> build. Pure copy.
• packages/cli/src/commands/preview.ts:262 — runLocalStudioMode still spawns npx vite, which is intentional (this path runs against a user-installed @hyperframes/studio, not the monorepo) and consistent with using a universally available launcher. Just flagging that the pnpm→bun cleanup is correctly not extended here; no action needed.